Landing pad with charging and loading functionality for unmanned aerial vehicle

ABSTRACT

A landing pad for an unmanned aerial vehicle (“UAV”) is disclosed. The landing pad includes a support structure, a charging pad, and a plurality of movable UAV supports. The charging pad is coupled to the support structure and able to move relative to the support structure. The UAV supports are also coupled to the support structure and configured to translate along the support structure from a first position to a second position. When the UAV supports are in the first position, the charging pad supports the UAV. When the UAV supports are in the second position, the charging pad is lowered and the UAV supports then provide support to the UAV.

BACKGROUND

An unmanned vehicle, which may also be referred to as an autonomousvehicle, includes a vehicle capable of travel without aphysically-present human operator. An unmanned vehicle may operate in aremote-control mode, in an autonomous mode, or in a partially autonomousmode.

When an unmanned vehicle operates in a remote-control mode, a pilot ordriver that is at a remote location can control the unmanned vehicle viacommands that are sent to the unmanned vehicle via a wireless link. Whenthe unmanned vehicle operates in autonomous mode, the unmanned vehicletypically moves based on pre-programmed navigation waypoints, dynamicautomation systems, or a combination of these. Further, some unmannedvehicles can operate in both a remote-control mode and an autonomousmode, and in some instances may do so simultaneously. For instance, aremote pilot or driver may wish to leave navigation to an autonomoussystem while manually performing another task, such as operating amechanical system for picking up objects, as an example.

Various types of unmanned vehicles exist for various differentenvironments. For instance, unmanned vehicles exist for operation in theair, on the ground, underwater, and in space. Examples includequad-copters and tail-sitter unmanned aerial vehicles, among others.Unmanned vehicles also exist for hybrid operations in whichmulti-environment operation is possible. Examples of hybrid unmannedvehicles include an amphibious craft that is capable of operation onland as well as on water or a floatplane that is capable of landing onwater as well as on land. Other examples are also possible.

Unmanned aerial vehicles (UAVs) may be used to deliver a payload to, orretrieve a payload from, an individual or business. Additional systemsat the point of delivery or pick-up are helpful for users, workers,merchants and others to utilize and interact with UAVs. Other helpfulsystems may be at a central location where UAVs are stored and/orco-located with merchants. Loading/unloading systems and structures thatfacilitate safe and efficient delivery and/or pick-up of payloads, whilealso providing charging capabilities to the UAVs are disclosed herein.

SUMMARY

The present application discloses landing pads for an unmanned aerialvehicle (“UAV”), as well as related systems and methods. The landing padis part of a payload loading/unloading system that may also providecharging and other services to a UAV. UAVs are increasingly utilized fora wide array of delivery services and as such, dedicated structures thatincrease the ease of use, efficiency, reliability, and safety of suchdelivery services is necessary. Some UAVs utilize contact-based chargingin order to charge their batteries. For example, as described in U.S.Patent Publication No. 2019/0023133 (U.S. patent application Ser. No.15/654,644), which is hereby incorporated by reference, an electricallyconductive landing pad transfers electric power to one or more UAVbatteries via electrical contacts within the UAV. However, in order toload, unload, and/or otherwise service the UAV, access to the undersideof the UAV may be required. Beneficially, some examples described hereininclude a landing pad designed to not only charge a UAV, but also toprovide access to the underside of the UAV for loading and unloading ofpayloads along with allowing for other services that require similaraccess to the vehicle.

Example landing pads and related systems described herein may beinstalled on freestanding support structures, may be installed on orwithin existing structures such as building walls, rooftops, trucks,lamp posts, cell towers, warehouses, etc., or may be installed bymodifying an existing structure with aspects described herein.Beneficially, example landing pads and related systems described hereinmay be installed in a variety of locations without impeding everydaylife of merchants, customers, or other people, while increasing theefficiency of access to UAV delivery service to the same merchants,customers, or other people.

In one embodiment, a landing pad for a UAV is described. The landing padincludes a support structure, a charging pad, and a plurality of UAVsupports. The support structure may be freestanding or may be connectedto another structure. The charging pad includes a plurality ofelectrical contacts that are configured to transfer power to a UAV.Moreover, the charging pad is configured to move relative to the supportstructure. In some examples, more than one charging pad arecontemplated, and the one or more charging pads may be considered to behinged to the support structure. The UAV supports are coupled to thesupport structure. In some embodiments, the UAV supports include amotor, a pair of gears or wheels, and a roller/bar. The gears or wheelsare driven by the motor, and move along the support structure. The UAVsupports are configured to translate across the landing pad, and moreparticularly the support structure from a first position to a secondposition. When in the first position, the UAV supports provide the UAVaccess to the charging pad. Further, when the UAV supports are in thefirst position the charging pad supports the UAV. But when the UAVsupports are in the second position, the UAV supports provide support to(e.g., maintain a vertical position of), the UAV.

In another embodiment, a method is described. The method includessupporting a UAV above a ground surface by a charging pad of a landingpad. The method also includes a plurality of UAV supports moving acrossthe landing pad towards the UAV. Each of the UAV supports moves in adifferent direction in approaching the UAV. After the UAV supports movetowards the UAV, and in some examples, after coming into contact withthe UAV, the method includes moving the charging pad away from the UAVsuch that the UAV is no longer supported by the charging pad but isinstead supported by the UAV supports. The method may further includeproviding access to the underside of the UAV while the charging pad isaway from the UAV and the UAV is being supported by the UAV supports. Insome embodiments, the method includes other aspects including landingthe UAV, charging the UAV, and loading a payload to the UAV, amongothers.

In yet another embodiment, a system is provided. The system includes aUAV and a landing pad. The UAV includes a fuselage and a retractabletether. A payload coupling apparatus is connected to a distal end of thetether, while the proximate end of the tether is connected to the UAV.In some examples, the proximate end of the tether is connected to awinch system of the UAV. The landing pad of the system includes asupport structure, a charging pad, and a plurality of UAV supports. Thecharging pad includes a plurality of electrical contacts that areconfigured to transfer power to a UAV. Moreover, the charging pad isconfigured to move relative to the support structure. The UAV supportsare coupled to the support structure. The UAV supports translate acrossthe landing pad, and more particularly the support structure from afirst position to a second position. When in the first position, the UAVsupports provide the UAV access to the charging pad. Further, when theUAV supports are in the first position the charging pad supports theUAV. But when the UAV supports are in the second position, the UAVsupports provide support to (e.g., maintain a vertical position of), theUAV.

In further embodiments, any type of system or device could be used orconfigured as a means for performing functions of any of the methodsdescribed herein (or any portions of the methods described herein). Forexample, a system for landing, charging, supporting, loading, and/orunloading a UAV includes means to land, charge, support, load, and/orunload the UAV.

These as well as other aspects, advantages, and alternatives will becomeapparent to those of ordinary skill in the art by reading the followingdetailed description, with reference where appropriate to theaccompanying drawings. Further, it should be understood that thedescription provided in this summary section and elsewhere in thisdocument is intended to illustrate the claimed subject matter by way ofexample and not by way of limitation

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a simplified illustration of an unmanned aerial vehicle(UAV), according to an example embodiment.

FIG. 1B is a simplified illustration of a UAV, according to an exampleembodiment.

FIG. 1C is a simplified illustration of a UAV, according to an exampleembodiment.

FIG. 1D is a simplified illustration of a UAV, according to an exampleembodiment.

FIG. 1E is a simplified illustration of a UAV, according to an exampleembodiment.

FIG. 2 is a simplified block diagram illustrating components of anunmanned aerial vehicle, according to an example embodiment.

FIG. 3 is a simplified block diagram illustrating a UAV system,according to an example embodiment.

FIG. 4 illustrates a payload loading system, according to an exampleembodiment.

FIG. 5 illustrates payload loading systems, including example landingpads, installed in various ways on a building structure, according to anexample embodiment.

FIG. 6A illustrates a UAV on a landing pad, according to an exampleembodiment.

FIG. 6B illustrates a UAV on a landing pad with a plurality of UAVsupports, according to an example embodiment.

FIG. 6C illustrates a UAV supported by a plurality of UAV supports on alanding pad, according to an example embodiment.

FIG. 6D illustrates a UAV supported by a plurality of UAV supports witha charging pad that has moved away from the UAV, according to an exampleembodiment.

FIG. 6E illustrates a UAV supported by a plurality of UAV supports andthe UAV having deployed a payload coupling apparatus, according to anexample embodiment.

FIG. 6F illustrates a UAV supported by a plurality of UAV supports andthe UAV having picked up a payload, according to an example embodiment.

FIG. 6G illustrates a UAV departing from a landing pad, according to anexample embodiment.

FIG. 7 illustrates a UAV supported by a plurality of UAV supports with acharging pad that has moved away from the UAV, according to an exampleembodiment.

FIG. 8 is a simplified block diagram illustrating a method relating tosupporting a UAV on a landing pad, according to an example embodiment.

DETAILED DESCRIPTION

Example methods, systems, and devices are described herein. Any exampleembodiment or feature described herein is not necessarily to beconstrued as preferred or advantageous over other embodiments orfeatures. The example embodiments described herein are not meant to belimiting. It will be readily understood that certain aspects of thedisclosed systems and methods can be arranged and combined in a widevariety of different configurations, all of which are contemplatedherein.

Furthermore, the particular arrangements shown in the Figures should notbe viewed as limiting. It should be understood that other embodimentsmight include more or less of each element shown in a given Figure.Further, some of the illustrated elements may be combined or omitted.Yet further, an example embodiment may include elements that are notillustrated in the Figures.

I. OVERVIEW

The embodiments described herein relate to landing pads for unmannedaerial vehicles (“UAVs”). The landing pads described herein may be partof a payload loading structure or system, such as those described inU.S. Pat. No. 10,604,252, which is hereby incorporated by reference.Aspects written in terms of “loading,” such as a payload loadingstructure, should be understood to not be limited to “loading” functionsor scenarios only. For example, unloading, maintenance, charging, andother interactions between a user, a UAV, a payload loading structure,and/or related components may occur at a payload loading structure oraspect thereof.

Exemplary embodiments may include, be implemented as part of, or take ofthe form of an aerial vehicle or system related thereto. In exampleembodiments, a UAV may include rotor units operable to provide thrust orlift for the UAV for transport and delivery of a payload. Herein, theterms “unmanned aerial vehicle” and “UAV” refer to any autonomous orsemi-autonomous vehicle that is capable of performing some functionswithout a physically present human pilot. A UAV can take various forms.For example, a UAV may take the form of a fixed-wing aircraft, a glideraircraft, a tail-sitter aircraft, a jet aircraft, a ducted fan aircraft,a lighter-than-air dirigible such as a blimp or steerable balloon, arotorcraft such as a helicopter or multicopter, and/or an ornithopter,among other possibilities. Further, the terms “drone,” “unmanned aerialvehicle system” (UAVS), or “unmanned aerial system” (UAS) may also beused to refer to a UAV.

UAVs are increasingly being utilized to retrieve, carry, and deliverpayloads across a variety of industries. As such, infrastructure isneeded at pick-up and drop-off locations so that merchants, customers,and other users can utilize UAV delivery services. More particularly,payload loading systems may provide known, accessible, dedicated, andsafe areas for a person or other device utilizing a UAV delivery serviceto load or unload a payload. Payload loading systems may include alanding pad (which may also be considered a landing platform).

UAVs depend on battery power in order to carry-out various operations.Rather than having separate charging structures/stations and payloadloading structures, advantageously, a landing pad that has chargingcapabilities but also provides access to the underside of the UAV aspart of a single apparatus, is described herein. Charging, or rechargingis accomplished via contact between a charging pad and electricalcontacts on the body of the UAV. In addition to recharging a battery, acharging pad included as part of a landing pad may provide the means forthe UAV to complete other tasks, such as uploading or downloadinginformation from a network, among other possibilities. By also providingaccess to the underside of the UAV, the UAV is able to deploy itstether, pick-up (or drop-off) a payload (or package), or otherwise beserviced. Other UAVs may depend on another fuel source for power, andrefueling of that fuel is contemplated within the scope of thisdisclosure.

In order to provide access to the underside of the UAV, the landing padincludes a charging pad and a support structure, and the charging padmay move away from the support structure. In some regards, the chargingpad may move similar to a “trapdoor” or other doors orientatedhorizontally such that something passes through vertically. In order tostill support the UAV, the landing pad also includes movable supportsthat maintain the UAV's position above the ground, but still provideaccess to the underside of the UAV once the charging pad has moved away.While the UAV could hover above the open cavity left behind after thecharging pad moves away from the UAV, by using other supports,beneficially, the UAV's battery life is saved.

Beneficially, landing pads as part of payload loading structures, asdescribed, may provide more people with access to UAV delivery services.Additionally, landing pads described herein may reduce the risk ofinjury to humans by increasing the distance between the UAV and thepoint of interaction (i.e., loading and unloading of a payload at atarget location, replacing batteries, etc.) and providing access to theunderside of the UAV when moving components (e.g., propellers) may be ona topside of the UAV. Moreover, inherent features of the landing padsdescribed may allow for installation of such systems (or related devicesand components thereof) in a variety of locations without impedingeveryday life of people.

The Figures described in detail below are for illustrative purposes onlyand may not reflect all components or connections. Further, asillustrations the Figures may not reflect actual operating conditions,but are merely to illustrate embodiments described. Further still, therelative dimensions and angles in the Figures may not be to scale, butare merely to illustrate the embodiments described.

II. ILLUSTRATIVE UNMANNED VEHICLES

FIG. 1A is an isometric view of an example UAV 100. UAV 100 includeswing 102, booms 104, and a fuselage 106. Wings 102 may be stationary andmay generate lift based on the wing shape and the UAV's forwardairspeed. For instance, the two wings 102 may have an airfoil-shapedcross section to produce an aerodynamic force on UAV 100. In someembodiments, wing 102 may carry horizontal propulsion units 108, andbooms 104 may carry vertical propulsion units 110. In operation, powerfor the propulsion units may be provided from a battery compartment 112of fuselage 106. In some embodiments, fuselage 106 also includes anavionics compartment 114, an additional battery compartment (not shown)and/or a delivery unit (not shown, e.g., a winch system) for handlingthe payload. In some embodiments, fuselage 106 is modular, and two ormore compartments (e.g., battery compartment 112, avionics compartment114, other payload and delivery compartments) are detachable from eachother and securable to each other (e.g., mechanically, magnetically, orotherwise) to contiguously form at least a portion of fuselage 106.

In some embodiments, booms 104 terminate in rudders 116 for improved yawcontrol of UAV 100. Further, wings 102 may terminate in wing tips 117for improved control of lift of the UAV.

In the illustrated configuration, UAV 100 includes a structural frame.The structural frame may be referred to as a “structural H-frame” or an“H-frame” (not shown) of the UAV. The H-frame may include, within wings102, a wing spar (not shown) and, within booms 104, boom carriers (notshown). In some embodiments the wing spar and the boom carriers may bemade of carbon fiber, hard plastic, aluminum, light metal alloys, orother materials. The wing spar and the boom carriers may be connectedwith clamps. The wing spar may include pre-drilled holes for horizontalpropulsion units 108, and the boom carriers may include pre-drilledholes for vertical propulsion units 110.

In some embodiments, fuselage 106 may be removably attached to theH-frame (e.g., attached to the wing spar by clamps, configured withgrooves, protrusions or other features to mate with correspondingH-frame features, etc.). In other embodiments, fuselage 106 similarlymay be removably attached to wings 102. The removable attachment offuselage 106 may improve quality and or modularity of UAV 100. Forexample, electrical/mechanical components and/or subsystems of fuselage106 may be tested separately from, and before being attached to, theH-frame. Similarly, printed circuit boards (PCBs) 118 may be testedseparately from, and before being attached to, the boom carriers,therefore eliminating defective parts/subassemblies prior to completingthe UAV. For example, components of fuselage 106 (e.g., avionics,battery unit, delivery units, an additional battery compartment, etc.)may be electrically tested before fuselage 106 is mounted to theH-frame. Furthermore, the motors and the electronics of PCBs 118 mayalso be electrically tested before the final assembly. Generally, theidentification of the defective parts and subassemblies early in theassembly process lowers the overall cost and lead time of the UAV.Furthermore, different types/models of fuselage 106 may be attached tothe H-frame, therefore improving the modularity of the design. Suchmodularity allows these various parts of UAV 100 to be upgraded withouta substantial overhaul to the manufacturing process.

In some embodiments, a wing shell and boom shells may be attached to theH-frame by adhesive elements (e.g., adhesive tape, double-sided adhesivetape, glue, etc.). Therefore, multiple shells may be attached to theH-frame instead of having a monolithic body sprayed onto the H-frame. Insome embodiments, the presence of the multiple shells reduces thestresses induced by the coefficient of thermal expansion of thestructural frame of the UAV. As a result, the UAV may have betterdimensional accuracy and/or improved reliability.

Moreover, in at least some embodiments, the same H-frame may be usedwith the wing shell and/or boom shells having different size and/ordesign, therefore improving the modularity and versatility of the UAVdesigns. The wing shell and/or the boom shells may be made of relativelylight polymers (e.g., closed cell foam) covered by the harder, butrelatively thin, plastic skins.

The power and/or control signals from fuselage 106 may be routed to PCBs118 through cables running through fuselage 106, wings 102, and booms104. In the illustrated embodiment, UAV 100 has four PCBs, but othernumbers of PCBs are also possible. For example, UAV 100 may include twoPCBs, one per the boom. The PCBs carry electronic components 119including, for example, power converters, controllers, memory, passivecomponents, etc. In operation, propulsion units 108 and 110 of UAV 100are electrically connected to the PCBs.

Many variations on the illustrated UAV are possible. For instance,fixed-wing UAVs may include more or fewer rotor units (vertical orhorizontal), and/or may utilize a ducted fan or multiple ducted fans forpropulsion. Further, UAVs with more wings (e.g., an “x-wing”configuration with four wings), are also possible. Although FIG. 1illustrates two wings 102, two booms 104, two horizontal propulsionunits 108, and six vertical propulsion units 110 per boom 104, it shouldbe appreciated that other variants of UAV 100 may be implemented withmore or less of these components. For example, UAV 100 may include fourwings 102, four booms 104, and more or less propulsion units (horizontalor vertical).

Similarly, FIG. 1B shows another example of a fixed-wing UAV 120. Thefixed-wing UAV 120 includes a fuselage 122, two wings 124 with anairfoil-shaped cross section to provide lift for the UAV 120, a verticalstabilizer 126 (or fin) to stabilize the plane's yaw (turn left orright), a horizontal stabilizer 128 (also referred to as an elevator ortailplane) to stabilize pitch (tilt up or down), landing gear 130, and apropulsion unit 132, which can include a motor, shaft, and propeller.

FIG. 1C shows an example of a UAV 140 with a propeller in a pusherconfiguration. The term “pusher” refers to the fact that a propulsionunit 142 is mounted at the back of the UAV and “pushes” the vehicleforward, in contrast to the propulsion unit being mounted at the frontof the UAV. Similar to the description provided for FIGS. 1A and 1B,FIG. 1C depicts common structures used in a pusher plane, including afuselage 144, two wings 146, vertical stabilizers 148, and thepropulsion unit 142, which can include a motor, shaft, and propeller.

FIG. 1D shows an example of a tail-sitter UAV 160. In the illustratedexample, the tail-sitter UAV 160 has fixed wings 162 to provide lift andallow the UAV 160 to glide horizontally (e.g., along the x-axis, in aposition that is approximately perpendicular to the position shown inFIG. 1D). However, the fixed wings 162 also allow the tail-sitter UAV160 to take off and land vertically on its own.

For example, at a launch site, the tail-sitter UAV 160 may be positionedvertically (as shown) with its fins 164 and/or wings 162 resting on theground and stabilizing the UAV 160 in the vertical position. Thetail-sitter UAV 160 may then take off by operating its propellers 166 togenerate an upward thrust (e.g., a thrust that is generally along they-axis). Once at a suitable altitude, the tail-sitter UAV 160 may useits flaps 168 to reorient itself in a horizontal position, such that itsfuselage 170 is closer to being aligned with the x-axis than the y-axis.Positioned horizontally, the propellers 166 may provide forward thrustso that the tail-sitter UAV 160 can fly in a similar manner as a typicalairplane.

Many variations on the illustrated fixed-wing UAVs are possible. Forinstance, fixed-wing UAVs may include more or fewer propellers, and/ormay utilize a ducted fan or multiple ducted fans for propulsion.Further, UAVs with more wings (e.g., an “x-wing” configuration with fourwings), with fewer wings, or even with no wings, are also possible.

As noted above, some embodiments may involve other types of UAVs, inaddition to or in the alternative to fixed-wing UAVs. For instance, FIG.1E shows an example of a rotorcraft that is commonly referred to as amulticopter 180. The multicopter 180 may also be referred to as aquadcopter, as it includes four rotors 182. It should be understood thatexample embodiments may involve a rotorcraft with more or fewer rotorsthan the multicopter 180. For example, a helicopter typically has tworotors. Other examples with three or more rotors are possible as well.Herein, the term “multicopter” refers to any rotorcraft having more thantwo rotors, and the term “helicopter” refers to rotorcraft having tworotors.

Referring to the multicopter 180 in greater detail, the four rotors 182provide propulsion and maneuverability for the multicopter 180. Morespecifically, each rotor 182 includes blades that are attached to amotor 184. Configured as such, the rotors 182 may allow the multicopter180 to take off and land vertically, to maneuver in any direction,and/or to hover. Further, the pitch of the blades may be adjusted as agroup and/or differentially, and may allow the multicopter 180 tocontrol its pitch, roll, yaw, and/or altitude.

It should be understood that references herein to an “unmanned” aerialvehicle or UAV can apply equally to autonomous and semi-autonomousaerial vehicles. In an autonomous implementation, all functionality ofthe aerial vehicle is automated; e.g., pre-programmed or controlled viareal-time computer functionality that responds to input from varioussensors and/or pre-determined information. In a semi-autonomousimplementation, some functions of an aerial vehicle may be controlled bya human operator, while other functions are carried out autonomously.Further, in some embodiments, a UAV may be configured to allow a remoteoperator to take over functions that can otherwise be controlledautonomously by the UAV. Yet further, a given type of function may becontrolled remotely at one level of abstraction and performedautonomously at another level of abstraction. For example, a remoteoperator could control high level navigation decisions for a UAV, suchas by specifying that the UAV should travel from one location to another(e.g., from a warehouse in a suburban area to a delivery address in anearby city), while the UAV's navigation system autonomously controlsmore fine-grained navigation decisions, such as the specific route totake between the two locations, specific flight controls to achieve theroute and avoid obstacles while navigating the route, and so on.

More generally, it should be understood that the example UAVs describedherein are not intended to be limiting. Example embodiments may relateto, be implemented within, or take the form of any type of unmannedaerial vehicle.

III. ILLUSTRATIVE UAV COMPONENTS

FIG. 2 is a simplified block diagram illustrating components of a UAV200, according to an example embodiment. UAV 200 may take the form of,or be similar in form to, one of the UAVs 100, 120, 140, 160, and 180described in reference to FIGS. 1A-1E. However, UAV 200 may also takeother forms.

UAV 200 may include various types of sensors, and may include acomputing system configured to provide the functionality describedherein. In the illustrated embodiment, the sensors of UAV 200 include aninertial measurement unit (IMU) 202, ultrasonic sensor(s) 204, and a GPS206, among other possible sensors and sensing systems.

In the illustrated embodiment, UAV 200 also includes one or moreprocessors 208. A processor 208 may be a general-purpose processor or aspecial purpose processor (e.g., digital signal processors, applicationspecific integrated circuits, etc.). The one or more processors 208 canbe configured to execute computer-readable program instructions 212 thatare stored in the data storage 210 and are executable to provide thefunctionality of a UAV described herein.

The data storage 210 may include or take the form of one or morecomputer-readable storage media that can be read or accessed by at leastone processor 208. The one or more computer-readable storage media caninclude volatile and/or non-volatile storage components, such asoptical, magnetic, organic or other memory or disc storage, which can beintegrated in whole or in part with at least one of the one or moreprocessors 208. In some embodiments, the data storage 210 can beimplemented using a single physical device (e.g., one optical, magnetic,organic or other memory or disc storage unit), while in otherembodiments, the data storage 210 can be implemented using two or morephysical devices.

As noted, the data storage 210 can include computer-readable programinstructions 212 and perhaps additional data, such as diagnostic data ofthe UAV 200. As such, the data storage 210 may include programinstructions 212 to perform or facilitate some or all of the UAVfunctionality described herein. For instance, in the illustratedembodiment, program instructions 212 include a navigation module 214 anda tether control module 216.

In some embodiments, the control system 1120 may take the form ofprogram instructions 212 and the one or more processors 208.

A. Sensors

In an illustrative embodiment, IMU 202 may include both an accelerometerand a gyroscope, which may be used together to determine an orientationof the UAV 200. In particular, the accelerometer can measure theorientation of the vehicle with respect to earth, while the gyroscopemeasures the rate of rotation around an axis. IMUs are commerciallyavailable in low-cost, low-power packages. For instance, an IMU 202 maytake the form of or include a miniaturized MicroElectroMechanical System(MEMS) or a NanoElectroMechanical System (NEMS). Other types of IMUs mayalso be utilized.

An IMU 202 may include other sensors, in addition to accelerometers andgyroscopes, which may help to better determine position and/or help toincrease autonomy of the UAV 200. Two examples of such sensors aremagnetometers and pressure sensors. In some embodiments, a UAV mayinclude a low-power, digital 3-axis magnetometer, which can be used torealize an orientation independent electronic compass for accurateheading information. However, other types of magnetometers may beutilized as well. Other examples are also possible. Further, note that aUAV could include some or all of the above-described inertia sensors asseparate components from an IMU.

UAV 200 may also include a pressure sensor or barometer, which can beused to determine the altitude of the UAV 200. Alternatively, othersensors, such as sonic altimeters or radar altimeters, can be used toprovide an indication of altitude, which may help to improve theaccuracy of and/or prevent drift of an IMU.

In a further aspect, UAV 200 may include one or more sensors that allowthe UAV to sense objects in the environment. For instance, in theillustrated embodiment, UAV 200 includes ultrasonic sensor(s) 204.Ultrasonic sensor(s) 204 can determine the distance to an object bygenerating sound waves and determining the time interval betweentransmission of the wave and receiving the corresponding echo off anobject. A typical application of an ultrasonic sensor for unmannedvehicles or IMUs is low-level altitude control and obstacle avoidance.An ultrasonic sensor can also be used for vehicles that need to hover ata certain height or need to be capable of detecting obstacles. Othersystems can be used to determine, sense the presence of, and/ordetermine the distance to nearby objects, such as a light detection andranging (LIDAR) system, laser detection and ranging (LADAR) system,and/or an infrared or forward-looking infrared (FLIR) system, amongother possibilities.

In some embodiments, UAV 200 may also include one or more imagingsystem(s). For example, one or more still and/or video cameras may beutilized by UAV 200 to capture image data from the UAV's environment. Asa specific example, charge-coupled device (CCD) cameras or complementarymetal-oxide-semiconductor (CMOS) cameras can be used with unmannedvehicles. Such imaging sensor(s) have numerous possible applications,such as obstacle avoidance, localization techniques, ground tracking formore accurate navigation (e.g., by applying optical flow techniques toimages), video feedback, and/or image recognition and processing, amongother possibilities.

UAV 200 may also include a GPS receiver 206. The GPS receiver 206 may beconfigured to provide data that is typical of well-known GPS systems,such as the GPS coordinates of the UAV 200. Such GPS data may beutilized by the UAV 200 for various functions. As such, the UAV may useits GPS receiver 206 to help navigate to the caller's location, asindicated, at least in part, by the GPS coordinates provided by theirmobile device. Other examples are also possible.

B. Navigation and Location Determination

The navigation module 214 may provide functionality that allows the UAV200 to, e.g., move about its environment and reach a desired location.To do so, the navigation module 214 may control the altitude and/ordirection of flight by controlling the mechanical features of the UAVthat affect flight (e.g., its rudder(s), elevator(s), aileron(s), and/orthe speed of its propeller(s)).

In order to navigate the UAV 200 to a target location, the navigationmodule 214 may implement various navigation techniques, such asmap-based navigation and localization-based navigation, for instance.With map-based navigation, the UAV 200 may be provided with a map of itsenvironment, which may then be used to navigate to a particular locationon the map. With localization-based navigation, the UAV 200 may becapable of navigating in an unknown environment using localization.Localization-based navigation may involve the UAV 200 building its ownmap of its environment and calculating its position within the mapand/or the position of objects in the environment. For example, as a UAV200 moves throughout its environment, the UAV 200 may continuously uselocalization to update its map of the environment. This continuousmapping process may be referred to as simultaneous localization andmapping (SLAM). Other navigation techniques may also be utilized.

In some embodiments, the navigation module 214 may navigate using atechnique that relies on waypoints. In particular, waypoints are sets ofcoordinates that identify points in physical space. For instance, anair-navigation waypoint may be defined by a certain latitude, longitude,and altitude. Accordingly, navigation module 214 may cause UAV 200 tomove from waypoint to waypoint, in order to ultimately travel to a finaldestination (e.g., a final waypoint in a sequence of waypoints).

In a further aspect, the navigation module 214 and/or other componentsand systems of the UAV 200 may be configured for “localization” to moreprecisely navigate to the scene of a target location. More specifically,it may be desirable in certain situations for a UAV to be within athreshold distance of the target location where a payload 228 is beingdelivered by a UAV (e.g., within a few feet of the target destination).To this end, a UAV may use a two-tiered approach in which it uses amore-general location-determination technique to navigate to a generalarea that is associated with the target location, and then use amore-refined location-determination technique to identify and/ornavigate to the target location within the general area.

For example, the UAV 200 may navigate to the general area of a targetdestination where a payload 228 is being delivered using waypointsand/or map-based navigation. The UAV may then switch to a mode in whichit utilizes a localization process to locate and travel to a morespecific location. For instance, if the UAV 200 is to deliver a payloadto a user's home, the UAV 200 may need to be substantially close to thetarget location in order to avoid delivery of the payload to undesiredareas (e.g., onto a roof, into a pool, onto a neighbor's property,etc.). However, a GPS signal may only get the UAV 200 so far (e.g.,within a block of the user's home). A more preciselocation-determination technique may then be used to find the specifictarget location.

Various types of location-determination techniques may be used toaccomplish localization of the target delivery location once the UAV 200has navigated to the general area of the target delivery location. Forinstance, the UAV 200 may be equipped with one or more sensory systems,such as, for example, ultrasonic sensors 204, infrared sensors (notshown), and/or other sensors, which may provide input that thenavigation module 214 utilizes to navigate autonomously orsemi-autonomously to the specific target location.

As another example, once the UAV 200 reaches the general area of thetarget delivery location (or of a moving subject such as a person ortheir mobile device), the UAV 200 may switch to a “fly-by-wire” modewhere it is controlled, at least in part, by a remote operator, who cannavigate the UAV 200 to the specific target location. To this end,sensory data from the UAV 200 may be sent to the remote operator toassist them in navigating the UAV 200 to the specific location.

As yet another example, the UAV 200 may include a module that is able tosignal to a passer-by for assistance in either reaching the specifictarget delivery location; for example, the UAV 200 may display a visualmessage requesting such assistance in a graphic display, play an audiomessage or tone through speakers to indicate the need for suchassistance, among other possibilities. Such a visual or audio messagemight indicate that assistance is needed in delivering the UAV 200 to aparticular person or a particular location, and might provideinformation to assist the passer-by in delivering the UAV 200 to theperson or location (e.g., a description or picture of the person orlocation, and/or the person or location's name), among otherpossibilities. Such a feature can be useful in a scenario in which theUAV is unable to use sensory functions or another location-determinationtechnique to reach the specific target location. However, this featureis not limited to such scenarios.

In some embodiments, once the UAV 200 arrives at the general area of atarget delivery location, the UAV 200 may utilize a beacon from a user'sremote device (e.g., the user's mobile phone) to locate the person. Sucha beacon may take various forms. As an example, consider the scenariowhere a remote device, such as the mobile phone of a person whorequested a UAV delivery, is able to send out directional signals (e.g.,via an RF signal, a light signal and/or an audio signal). In thisscenario, the UAV 200 may be configured to navigate by “sourcing” suchdirectional signals—in other words, by determining where the signal isstrongest and navigating accordingly. As another example, a mobiledevice can emit a frequency, either in the human range or outside thehuman range, and the UAV 200 can listen for that frequency and navigateaccordingly. As a related example, if the UAV 200 is listening forspoken commands, then the UAV 200 could utilize spoken statements, suchas “I'm over here!” to source the specific location of the personrequesting delivery of a payload.

In an alternative arrangement, a navigation module may be implemented ata remote computing device, which communicates wirelessly with the UAV200. The remote computing device may receive data indicating theoperational state of the UAV 200, sensor data from the UAV 200 thatallows it to assess the environmental conditions being experienced bythe UAV 200, and/or location information for the UAV 200. Provided withsuch information, the remote computing device may determine altitudinaland/or directional adjustments that should be made by the UAV 200 and/ormay determine how the UAV 200 should adjust its mechanical features(e.g., its rudder(s), elevator(s), aileron(s), and/or the speed of itspropeller(s)) in order to effectuate such movements. The remotecomputing system may then communicate such adjustments to the UAV 200 soit can move in the determined manner.

C. Communication Systems

In a further aspect, the UAV 200 includes one or more communicationsystems 218. The communications systems 218 may include one or morewireless interfaces and/or one or more wireline interfaces, which allowthe UAV 200 to communicate via one or more networks. Such wirelessinterfaces may provide for communication under one or more wirelesscommunication protocols, such as Bluetooth, WiFi (e.g., an IEEE 802.11protocol), Long-Term Evolution (LTE), WiMAX (e.g., an IEEE 802.16standard), a radio-frequency ID (RFID) protocol, near-fieldcommunication (NFC), and/or other wireless communication protocols. Suchwireline interfaces may include an Ethernet interface, a UniversalSerial Bus (USB) interface, or similar interface to communicate via awire, a twisted pair of wires, a coaxial cable, an optical link, afiber-optic link, or other physical connection to a wireline network.

In some embodiments, a UAV 200 may include communication systems 218that allow for both short-range communication and long-rangecommunication. For example, the UAV 200 may be configured forshort-range communications using Bluetooth and for long-rangecommunications under a CDMA protocol. In such an embodiment, the UAV 200may be configured to function as a “hot spot;” or in other words, as agateway or proxy between a remote support device and one or more datanetworks, such as a cellular network and/or the Internet. Configured assuch, the UAV 200 may facilitate data communications that the remotesupport device would otherwise be unable to perform by itself.

For example, the UAV 200 may provide a WiFi connection to a remotedevice, and serve as a proxy or gateway to a cellular service provider'sdata network, which the UAV might connect to under an LTE or a 3Gprotocol, for instance. The UAV 200 could also serve as a proxy orgateway to a high-altitude balloon network, a satellite network, or acombination of these networks, among others, which a remote device mightnot be able to otherwise access.

D. Power Systems

In a further aspect, the UAV 200 may include power system(s) 220. Thepower system 220 may include one or more batteries for providing powerto the UAV 200. In one example, the one or more batteries may berechargeable and each battery may be recharged via a wired connectionbetween the battery and a power supply and/or via a wireless chargingsystem, such as an inductive charging system that applies an externaltime-varying magnetic field to an internal battery.

E. Payload Delivery

The UAV 200 may employ various systems and configurations in order totransport and deliver a payload 228. In some implementations, thepayload 228 of a given UAV 200 may include or take the form of a“package” designed to transport various goods to a target deliverylocation. For example, the UAV 200 can include a compartment, in whichan item or items may be transported. Such a package may one or more fooditems, purchased goods, medical items, or any other object(s) having asize and weight suitable to be transported between two locations by theUAV. In other embodiments, a payload 228 may simply be the one or moreitems that are being delivered (e.g., without any package housing theitems).

In some embodiments, the payload 228 may be attached to the UAV andlocated substantially outside of the UAV during some or all of a flightby the UAV. For example, the package may be tethered or otherwisereleasably attached below the UAV during flight to a target location. Inan embodiment where a package carries goods below the UAV, the packagemay include various features that protect its contents from theenvironment, reduce aerodynamic drag on the system, and prevent thecontents of the package from shifting during UAV flight.

For instance, when the payload 228 takes the form of a package fortransporting items, the package may include an outer shell constructedof water-resistant cardboard, plastic, or any other lightweight andwater-resistant material. Further, in order to reduce drag, the packagemay feature smooth surfaces with a pointed front that reduces thefrontal cross-sectional area. Further, the sides of the package maytaper from a wide bottom to a narrow top, which allows the package toserve as a narrow pylon that reduces interference effects on the wing(s)of the UAV. This may move some of the frontal area and volume of thepackage away from the wing(s) of the UAV, thereby preventing thereduction of lift on the wing(s) cause by the package. Yet further, insome embodiments, the outer shell of the package may be constructed froma single sheet of material in order to reduce air gaps or extramaterial, both of which may increase drag on the system. Additionally oralternatively, the package may include a stabilizer to dampen packageflutter. This reduction in flutter may allow the package to have a lessrigid connection to the UAV and may cause the contents of the package toshift less during flight.

In order to deliver the payload, the UAV may include a winch system 221controlled by the tether control module 216 in order to lower thepayload 228 to the ground while the UAV hovers above. As shown in FIG. 2, the winch system 221 may include a tether 224, and the tether 224 maybe coupled to the payload 228 by a payload coupling apparatus 226. Thetether 224 may be wound on a spool that is coupled to a motor 222 of theUAV. The motor 222 may take the form of a DC motor (e.g., a servo motor)that can be actively controlled by a speed controller. The tethercontrol module 216 can control the speed controller to cause the motor222 to rotate the spool, thereby unwinding or retracting the tether 224and lowering or raising the payload coupling apparatus 226. In practice,the speed controller may output a desired operating rate (e.g., adesired RPM) for the spool, which may correspond to the speed at whichthe tether 224 and payload 228 should be lowered towards the ground. Themotor 222 may then rotate the spool so that it maintains the desiredoperating rate.

In order to control the motor 222 via the speed controller, the tethercontrol module 216 may receive data from a speed sensor (e.g., anencoder) configured to convert a mechanical position to a representativeanalog or digital signal. In particular, the speed sensor may include arotary encoder that may provide information related to rotary position(and/or rotary movement) of a shaft of the motor or the spool coupled tothe motor, among other possibilities. Moreover, the speed sensor maytake the form of an absolute encoder and/or an incremental encoder,among others. So in an example implementation, as the motor 222 causesrotation of the spool, a rotary encoder may be used to measure thisrotation. In doing so, the rotary encoder may be used to convert arotary position to an analog or digital electronic signal used by thetether control module 216 to determine the amount of rotation of thespool from a fixed reference angle and/or to an analog or digitalelectronic signal that is representative of a new rotary position, amongother options. Other examples are also possible.

Based on the data from the speed sensor, the tether control module 216may determine a rotational speed of the motor 222 and/or the spool andresponsively control the motor 222 (e.g., by increasing or decreasing anelectrical current supplied to the motor 222) to cause the rotationalspeed of the motor 222 to match a desired speed. When adjusting themotor current, the magnitude of the current adjustment may be based on aproportional-integral-derivative (PID) calculation using the determinedand desired speeds of the motor 222. For instance, the magnitude of thecurrent adjustment may be based on a present difference, a pastdifference (based on accumulated error over time), and a futuredifference (based on current rates of change) between the determined anddesired speeds of the spool.

In some embodiments, the tether control module 216 may vary the rate atwhich the tether 224 and payload 228 are lowered to the ground. Forexample, the speed controller may change the desired operating rateaccording to a variable deployment-rate profile and/or in response toother factors in order to change the rate at which the payload 228descends toward the ground. To do so, the tether control module 216 mayadjust an amount of braking or an amount of friction that is applied tothe tether 224. For example, to vary the tether deployment rate, the UAV200 may include friction pads that can apply a variable amount ofpressure to the tether 224. As another example, the UAV 200 can includea motorized braking system that varies the rate at which the spool letsout the tether 224. Such a braking system may take the form of anelectromechanical system in which the motor 222 operates to slow therate at which the spool lets out the tether 224. Further, the motor 222may vary the amount by which it adjusts the speed (e.g., the RPM) of thespool, and thus may vary the deployment rate of the tether 224. Otherexamples are also possible.

In some embodiments, the tether control module 216 may be configured tolimit the motor current supplied to the motor 222 to a maximum value.With such a limit placed on the motor current, there may be situationswhere the motor 222 cannot operate at the desired operate specified bythe speed controller. For instance, as discussed in more detail below,there may be situations where the speed controller specifies a desiredoperating rate at which the motor 222 should retract the tether 224toward the UAV 200, but the motor current may be limited such that alarge enough downward force on the tether 224 would counteract theretracting force of the motor 222 and cause the tether 224 to unwindinstead. And as further discussed below, a limit on the motor currentmay be imposed and/or altered depending on an operational state of theUAV 200.

In some embodiments, the tether control module 216 may be configured todetermine a status of the tether 224 and/or the payload 228 based on theamount of current supplied to the motor 222. For instance, if a downwardforce is applied to the tether 224 (e.g., if the payload 228 is attachedto the tether 224 or if the tether 224 gets snagged on an object whenretracting toward the UAV 200), the tether control module 216 may needto increase the motor current in order to cause the determinedrotational speed of the motor 222 and/or spool to match the desiredspeed. Similarly, when the downward force is removed from the tether 224(e.g., upon delivery of the payload 228 or removal of a tether snag),the tether control module 216 may need to decrease the motor current inorder to cause the determined rotational speed of the motor 222 and/orspool to match the desired speed. As such, the tether control module 216may, based on the current supplied to the motor 222, determine if thepayload 228 is attached to the tether 224, if someone or something ispulling on the tether 224, and/or if the payload coupling apparatus 226is pressing against the UAV 200 after retracting the tether 224. Otherexamples are possible as well.

During delivery of the payload 228, the payload coupling apparatus 226can be configured to secure the payload 228 while being lowered from theUAV by the tether 224, and can be further configured to release thepayload 228 upon reaching ground level. The payload coupling apparatus226 can then be retracted to the UAV by reeling in the tether 224 usingthe motor 222.

In some implementations, the payload 228 may be passively released onceit is lowered to the ground. For example, a passive release mechanismmay include one or more swing arms adapted to retract into and extendfrom a housing. An extended swing arm may form a hook on which thepayload 228 may be attached. Upon lowering the release mechanism and thepayload 228 to the ground via a tether, a gravitational force as well asa downward inertial force on the release mechanism may cause the payload228 to detach from the hook allowing the release mechanism to be raisedupwards toward the UAV. The release mechanism may further include aspring mechanism that biases the swing arm to retract into the housingwhen there are no other external forces on the swing arm. For instance,a spring may exert a force on the swing arm that pushes or pulls theswing arm toward the housing such that the swing arm retracts into thehousing once the weight of the payload 228 no longer forces the swingarm to extend from the housing. Retracting the swing arm into thehousing may reduce the likelihood of the release mechanism snagging thepayload 228 or other nearby objects when raising the release mechanismtoward the UAV upon delivery of the payload 228.

Active payload release mechanisms are also possible. For example,sensors such as a barometric pressure based altimeter and/oraccelerometers may help to detect the position of the release mechanism(and the payload) relative to the ground. Data from the sensors can becommunicated back to the UAV and/or a control system over a wirelesslink and used to help in determining when the release mechanism hasreached ground level (e.g., by detecting a measurement with theaccelerometer that is characteristic of ground impact). In otherexamples, the UAV may determine that the payload has reached the groundbased on a weight sensor detecting a threshold low downward force on thetether and/or based on a threshold low measurement of power drawn by thewinch when lowering the payload.

Other systems and techniques for delivering a payload, in addition or inthe alternative to a tethered delivery system are also possible. Forexample, a UAV 200 could include an air-bag drop system or a parachutedrop system. Alternatively, a UAV 200 carrying a payload could simplyland on the ground at a delivery location. Other examples are alsopossible.

IV. ILLUSTRATIVE UAV DEPLOYMENT SYSTEMS

UAV systems may be implemented in order to provide various UAV-relatedservices. In particular, UAVs may be provided at a number of differentlaunch sites that may be in communication with regional and/or centralcontrol systems. Such a distributed UAV system may allow UAVs to bequickly deployed to provide services across a large geographic area(e.g., that is much larger than the flight range of any single UAV). Forexample, UAVs capable of carrying payloads may be distributed at anumber of launch sites across a large geographic area (possibly eventhroughout an entire country, or even worldwide), in order to provideon-demand transport of various items to locations throughout thegeographic area. FIG. 3 is a simplified block diagram illustrating adistributed UAV system 300, according to an example embodiment.

In the illustrative UAV system 300, an access system 302 may allow forinteraction with, control of, and/or utilization of a network of UAVs304. In some embodiments, an access system 302 may be a computing systemthat allows for human-controlled dispatch of UAVs 304. As such, thecontrol system may include or otherwise provide a user interface throughwhich a user can access and/or control the UAVs 304.

In some embodiments, dispatch of the UAVs 304 may additionally oralternatively be accomplished via one or more automated processes. Forinstance, the access system 302 may dispatch one of the UAVs 304 totransport a payload to a target location, and the UAV may autonomouslynavigate to the target location by utilizing various on-board sensors,such as a GPS receiver and/or other various navigational sensors.

Further, the access system 302 may provide for remote operation of aUAV. For instance, the access system 302 may allow an operator tocontrol the flight of a UAV via its user interface. As a specificexample, an operator may use the access system 302 to dispatch a UAV 304to a target location. The UAV 304 may then autonomously navigate to thegeneral area of the target location. At this point, the operator may usethe access system 302 to take control of the UAV 304 and navigate theUAV to the target location (e.g., to a particular person to whom apayload is being transported). Other examples of remote operation of aUAV are also possible.

In an illustrative embodiment, the UAVs 304 may take various forms. Forexample, each of the UAVs 304 may be a UAV such as those illustrated inFIGS. 1A-1E. However, UAV system 300 may also utilize other types ofUAVs without departing from the scope of the invention. In someimplementations, all of the UAVs 304 may be of the same or a similarconfiguration. However, in other implementations, the UAVs 304 mayinclude a number of different types of UAVs. For instance, the UAVs 304may include a number of types of UAVs, with each type of UAV beingconfigured for a different type or types of payload deliverycapabilities.

The UAV system 300 may further include a remote device 306, which maytake various forms. Generally, the remote device 306 may be any devicethrough which a direct or indirect request to dispatch a UAV can bemade. (Note that an indirect request may involve any communication thatmay be responded to by dispatching a UAV, such as requesting a packagedelivery). In an example embodiment, the remote device 306 may be amobile phone, tablet computer, laptop computer, personal computer, orany network-connected computing device. Further, in some instances, theremote device 306 may not be a computing device. As an example, astandard telephone, which allows for communication via plain oldtelephone service (POTS), may serve as the remote device 306. Othertypes of remote devices are also possible.

Further, the remote device 306 may be configured to communicate withaccess system 302 via one or more types of communication network(s) 308.For example, the remote device 306 may communicate with the accesssystem 302 (or a human operator of the access system 302) bycommunicating over a POTS network, a cellular network, and/or a datanetwork such as the Internet. Other types of networks may also beutilized.

In some embodiments, the remote device 306 may be configured to allow auser to request delivery of one or more items to a desired location. Forexample, a user could request UAV delivery of a package to their homevia their mobile phone, tablet, or laptop. As another example, a usercould request dynamic delivery to wherever they are located at the timeof delivery. To provide such dynamic delivery, the UAV system 300 mayreceive location information (e.g., GPS coordinates, etc.) from theuser's mobile phone, or any other device on the user's person, such thata UAV can navigate to the user's location (as indicated by their mobilephone).

In an illustrative arrangement, the central dispatch system 310 may be aserver or group of servers, which is configured to receive dispatchmessages requests and/or dispatch instructions from the access system302. Such dispatch messages may request or instruct the central dispatchsystem 310 to coordinate the deployment of UAVs to various targetlocations. The central dispatch system 310 may be further configured toroute such requests or instructions to one or more local dispatchsystems 312. To provide such functionality, the central dispatch system310 may communicate with the access system 302 via a data network, suchas the Internet or a private network that is established forcommunications between access systems and automated dispatch systems.

In the illustrated configuration, the central dispatch system 310 may beconfigured to coordinate the dispatch of UAVs 304 from a number ofdifferent local dispatch systems 312. As such, the central dispatchsystem 310 may keep track of which UAVs 304 are located at which localdispatch systems 312, which UAVs 304 are currently available fordeployment, and/or which services or operations each of the UAVs 304 isconfigured for (in the event that a UAV fleet includes multiple types ofUAVs configured for different services and/or operations). Additionallyor alternatively, each local dispatch system 312 may be configured totrack which of its associated UAVs 304 are currently available fordeployment and/or are currently in the midst of item transport.

In some cases, when the central dispatch system 310 receives a requestfor UAV-related service (e.g., transport of an item) from the accesssystem 302, the central dispatch system 310 may select a specific UAV304 to dispatch. The central dispatch system 310 may accordinglyinstruct the local dispatch system 312 that is associated with theselected UAV to dispatch the selected UAV. The local dispatch system 312may then operate its associated deployment system 314 to launch theselected UAV. In other cases, the central dispatch system 310 mayforward a request for a UAV-related service to a local dispatch system312 that is near the location where the support is requested and leavethe selection of a particular UAV 304 to the local dispatch system 312.

In an example configuration, the local dispatch system 312 may beimplemented as a computing system at the same location as the deploymentsystem(s) 314 that it controls. For example, the local dispatch system312 may be implemented by a computing system installed at a building,such as a warehouse, where the deployment system(s) 314 and UAV(s) 304that are associated with the particular local dispatch system 312 arealso located. In other embodiments, the local dispatch system 312 may beimplemented at a location that is remote to its associated deploymentsystem(s) 314 and UAV(s) 304.

Numerous variations on and alternatives to the illustrated configurationof the UAV system 300 are possible. For example, in some embodiments, auser of the remote device 306 could request delivery of a packagedirectly from the central dispatch system 310. To do so, an applicationmay be implemented on the remote device 306 that allows the user toprovide information regarding a requested delivery, and generate andsend a data message to request that the UAV system 300 provide thedelivery. In such an embodiment, the central dispatch system 310 mayinclude automated functionality to handle requests that are generated bysuch an application, evaluate such requests, and, if appropriate,coordinate with an appropriate local dispatch system 312 to deploy aUAV.

Further, some or all of the functionality that is attributed herein tothe central dispatch system 310, the local dispatch system(s) 312, theaccess system 302, and/or the deployment system(s) 314 may be combinedin a single system, implemented in a more complex system, and/orredistributed among the central dispatch system 310, the local dispatchsystem(s) 312, the access system 302, and/or the deployment system(s)314 in various ways.

Yet further, while each local dispatch system 312 is shown as having twoassociated deployment systems 314, a given local dispatch system 312 mayalternatively have more or fewer associated deployment systems 314.Similarly, while the central dispatch system 310 is shown as being incommunication with two local dispatch systems 312, the central dispatchsystem 310 may alternatively be in communication with more or fewerlocal dispatch systems 312.

In a further aspect, the deployment systems 314 may take various forms.In general, the deployment systems 314 may take the form of or includesystems for physically launching one or more of the UAVs 304. Suchlaunch systems may include features that provide for an automated UAVlaunch and/or features that allow for a human-assisted UAV launch.Further, the deployment systems 314 may each be configured to launch oneparticular UAV 304, or to launch multiple UAVs 304.

The deployment systems 314 may further be configured to provideadditional functions, including for example, diagnostic-relatedfunctions such as verifying system functionality of the UAV, verifyingfunctionality of devices that are housed within a UAV (e.g., a payloaddelivery apparatus), and/or maintaining devices or other items that arehoused in the UAV (e.g., by monitoring a status of a payload such as itstemperature, weight, etc.).

In some embodiments, the deployment systems 314 and their correspondingUAVs 304 (and possibly associated local dispatch systems 312) may bestrategically distributed throughout an area such as a city. Forexample, the deployment systems 314 may be strategically distributedsuch that each deployment system 314 is proximate to one or more payloadpickup locations (e.g., near a restaurant, store, or warehouse).However, the deployment systems 314 (and possibly the local dispatchsystems 312) may be distributed in other ways, depending upon theparticular implementation. As an additional example, kiosks that allowusers to transport packages via UAVs may be installed in variouslocations. Such kiosks may include UAV launch systems, and may allow auser to provide their package for loading onto a UAV and pay for UAVshipping services, among other possibilities. Other examples are alsopossible.

In a further aspect, the UAV system 300 may include or have access to auser-account database 316. The user-account database 316 may includedata for a number of user accounts, and which are each associated withone or more person. For a given user account, the user-account database316 may include data related to or useful in providing UAV-relatedservices. Typically, the user data associated with each user account isoptionally provided by an associated user and/or is collected with theassociated user's permission.

Further, in some embodiments, a person may be required to register for auser account with the UAV system 300, if they wish to be provided withUAV-related services by the UAVs 304 from UAV system 300. As such, theuser-account database 316 may include authorization information for agiven user account (e.g., a username and password), and/or otherinformation that may be used to authorize access to a user account.

In some embodiments, a person may associate one or more of their deviceswith their user account, such that they can access the services of UAVsystem 300. For example, when a person uses an associated mobile phone,e.g., to place a call to an operator of the access system 302 or send amessage requesting a UAV-related service to a dispatch system, the phonemay be identified via a unique device identification number, and thecall or message may then be attributed to the associated user account.Other examples are also possible.

V. ILLUSTRATIVE LANDING PADS AND LANDING PAD SYSTEMS

FIG. 4 illustrates a payload loading system 400. The payload loadingsystem 400 includes a landing pad 405. A UAV 410 may land on, takeofffrom, and/or hover over the landing pad 405 when operating a deliveryservice. The landing pad 405 may be coupled to a landing pad supportstructure 420. The delivery service may include pick-up, or drop-off, ofa payload 430. The UAV 410 includes a retractable tether 412 and apayload coupling apparatus 414. The tether 412 and the payload couplingapparatus 414 may be located within the UAV 410, such as within afuselage of the UAV 410. The payload coupling apparatus 414 may coupleto the payload 430 during the delivery service.

The UAV 410 may be similar to the UAVs described in FIGS. 1A-1E, FIG. 2, and FIG. 3 above. The UAV 410 includes components not depicted in FIG.4 . For example, the UAV 410 may further include a winch system. Thewinch system may be similar to winch systems described above, includingwinch system 221 of FIG. 2 , for example. The winch system may includethe tether 412. Other components of the UAV 410 may be similar in formand function as components described as part of the UAVs described inFIGS. 1A-1E.

The UAV 410 is coupled to a proximate end of the tether 412. Moreover,the proximate end of the tether 412 may be coupled to the winch systemof the UAV 410. The payload coupling apparatus 414 is coupled to theretractable tether 412 at a distal end of the tether 412. The payload430 is coupleable to the tether 412 at the payload coupling apparatus414.

In some instances, the landing pad 405 may include a charging pad.Moreover, the landing pad 405 may be on top of the landing pad supportstructure 420. As depicted in FIG. 4 , the landing pad support structure420 is coupled to a building 440 and supports the landing pad 405 abovea ground surface 450. In this regard, the landing pad 405 and landingpad support structure 420 may be configured to support the UAV 410 suchthat there is a safe amount of space between the UAV 410 and a user ofthe delivery service. While the landing pad support structure 420 iscoupled to the building 440 in FIG. 4 , the landing pad supportstructure 420 may be freestanding in other instances. Moreover, thelanding pad support structure 420 may couple the landing pad 405 to anexisting structure for support. Existing support structures that thelanding pad 405 may be coupled to include buildings, awnings, lampposts, mail boxes, restaurants, houses, flag poles, cars, trucks,vehicles, etc. In some embodiments, the landing pad 405 may be elevatedabove the ground surface 450, while in other instances the landing pad405 may be at or near the ground surface 450.

The landing pad 405 may be attached to a local electrical grid and/or anetwork in some embodiments. In some instances, the landing pad 405 maybe attached to a solar panel or other independent power source ratherthan the local electrical grid. In some examples, the landing pad 405may be attached to a local electrical grid and/or a network via thelanding pad support structure 420. As such, the landing pad 405, forexample via a component such as a charging pad, may provide electricalpower to the UAV and support the uploading/downloading of data.

When delivering the payload 430, the UAV 410 may pick up the payload 430from a warehouse, a storefront, a restaurant, or a user of the deliveryservice. The payload 430 is coupled to the payload coupling apparatus414. The payload coupling apparatus 414 includes means for attaching thepayload 430, for example, as described in U.S. Patent Publication No.2018/0072420 (U.S. patent application Ser. No. 15/389,074), which ishereby incorporated by reference.

Upon reaching the destination, the UAV 410 may land on the landing pad405 and pay out the tether 412. The tether 412 is coupled to the UAV 410at a first end and the payload coupling apparatus 414 at a second end.The payload 430 may reach a target location. The target location is athree-dimensional space that is easily accessed by a user, such as aconsumer or merchant. In some embodiments, the target location is at anergonomic position for a user to load or unload the payload 430. Oncethe payload 430 reaches the target location, the payload 430 is unloadedfrom the payload coupling apparatus 414. A user, merchant, robot, orother entity may unload the payload 430. When the payload 430 isunloaded to the payload coupling apparatus 414, one or more sensors onthe UAV 410 may detect a decrease in tension in the tether 412. At thistime, another payload may be loaded onto the payload coupling apparatus414. After unloading the payload 430, the UAV 410 may reel in the tether412.

In other examples, rather than dropping off the payload 430, the UAV 410may pick up and load the payload 430 after landing on the landing pad405. After landing, the UAV 410 may pay out the tether 412 such that thepayload coupling apparatus 414 reaches the target location where thepayload 430 can be coupled to the payload coupling apparatus 414. Thetether 412 may then reel in the tether 412 including the payload 430.

In some examples, the loading/unloading process may include reelingin/paying out the tether 412, payload coupling apparatus 414, andpossibly the payload 430 through a cavity in the landing pad 405. U.S.Pat. No. 10,604,252, incorporated by reference, more fully describespassing the tether 412 and the payload coupling apparatus 414 through acavity. In other examples, the loading/unloading process may not involvereeling in or paying out the tether 412, and instead the payload 430 maybe directly coupled to (e.g., clipped to) the UAV 410 or the payload 430may be loaded into a cavity of the fuselage of the UAV 410. For example,a consumer may be able to reach the underside of UAV 410 directly anduse of a tether would not be necessary. In such examples, the UAV 410may not include a tether or winch systems. In yet other examples, aconveyor or elevator or other means for transporting the payload 430to/from the UAV 410 are considered.

The payload loading system 400 may further include other features, suchas notifying a user when the UAV 410 has arrived to pick-up (ordrop-off) the payload 430. In some embodiments, the payload loadingsystem 400, including the landing pad support structure 420 may includea user interface to assist the user in preparing for delivery orpick-up. For example, a merchant may enter an address or other userinformation into the payload loading system 400 such that the UAV 410 isprovided with relevant information to carry out the delivery of thepayload 430. In other examples, the payload loading system 400 or anoperator thereof may be notified that the UAV 410 is charged and readyto receive the payload 430. In such examples, the UAV 410's preparednessmay be indicated via an indicator lamp, the payload coupling apparatus414 being lowered, or a software signal to a payload-aircraftassignment/dispatching system, among other examples.

As depicted in FIG. 4 , the UAV 410 has landed on the landing pad 405.While landed, the UAV 410 may charge or replace batteries, and/orcommunicate with other aspects of a UAV system. Additionally, whilelanded, the UAV 410 may wait for a user or other device to load (orunload) the payload 430 onto the payload coupling apparatus 414. In someexamples, loading the payload 430 may occur after charging the UAV 410is completed. At least one advantage of the payload loading system 400being configured to support the landing of the UAV 410 is that loadingthe payload 430 while the UAV 410 is landed saves battery energy of theUAV 410.

FIG. 5 illustrates a payload loading system 500 that includes a rooflanding pad 505, a first awning landing pad 506, a cantilevered landingpad 507, and a second awning landing pad 508. As shown in FIG. 5 , aplurality of UAVs 510 may land on one or more of the landing padsdescribed herein. The landing pads are coupled to a building 520. Insome instances, the landing pads in FIG. 5 are coupled to the building520 via a support structure, such as the landing pad support structure420 in FIG. 4 , among other examples.

As illustrated in FIG. 5 , the payload loading system 500 includinglanding pads may be a structure as part of a building or warehouse.Within examples, landings pads are coupled to, or included as part of amerchant module. The merchant module may include a warehouse ordistribution center. A merchant may sell or execute deliveries out via aUAV delivery system out of the merchant module including the landingpads. Although the landing pads are shown on the outside of the building520, it should be noted that the landing pads could also be installedinside the building 520 and UAVs could travel in and out of the building520.

While FIG. 5 depicts the building 520 and is generally considered partof a merchant module, it is also considered herein that otherstructures, including trucks, residences, stores, and other commonstructures in a community may be designated as a location where UAVdelivery service may be desirable and thus a corresponding payloadloading system including one or more landing pads may be installed. Asshown in FIG. 5 , the landing pads described herein may be installed ina variety of ways to existing and new structures. Such structures may bededicated to delivery services, or may be fitted to include a landingpad in a convenient location for a network of UAVs. Other similar designconsiderations are contemplated.

More particularly, FIG. 5 depicts the roof landing pad 505. The rooflanding pad 505 may be installed on a roof of the building 520 andpayloads may pass through an opening, a cavity, or a window of thebuilding 520. FIG. 5 also depicts the first awning landing pad 506 thatis arranged over a window in the building 520. Merchants or customersmay interact with the UAV 510 via the window under the first awninglanding pad 506. Similarly, FIG. 5 depicts the cantilevered landing pad507. The cantilevered landing pad 507 may be directly coupled to thebuilding 520 and, being cantilever off of the building 520, thecantilevered landing pad 507 may support the entirety of the landing padand any UAVs 510 landed thereon. Merchants or customers may interactwith the UAVs 510 on the cantilevered landing pad 507 by walking underthe landing pad. The second awning landing pad 508 is another exampleembodiment. A payload 530 may be made available by a merchant for pickupby one of the UAVs 510. The payload 530 may be loaded onto the UAVs 510by a person or machine upon being prepared for delivery by the UAVs 510.

While FIG. 5 depicts various landing pads installed on and as part ofthe building 520, other implementations are considered herein. Forexample, landing pads described herein may be portable and/or may beused independent of any other support. In other examples, landing padsmay be installed as part of systems not otherwise depicted. For example,in another embodiment landing pads with charging capabilities may bebuilt into a floor of an upper level of a hanger or warehouse. Operatorsand package loading may occur below on a lower level while the UAVs areon the upper level. Movable charge pads as part of the landing padscould be built into the floor structure itself. Other implementations ofthe landing pad described herein will become apparent to a person ofskill in the art.

Continuing with the Figures, FIGS. 6A-6G depict a landing pad 600,according to an example embodiment. The landing pad 600 including acharging pad 605, a support structure 620, and a plurality of UAVsupports 630A, 630B, 630C, and 630D. The charging pad 605 may include aplurality of electrical contacts 607. One or more hinge(s) 609 maycouple the charging pad 605 to the support structure 620. A UAV 610includes a retractable tether 612 (see FIG. 6E) and a payload couplingapparatus 614 (see FIG. 6E). The payload coupling apparatus 614 maycouple to a payload 616 (see FIG. 6F). The UAV 610 may also include afuselage 618. The support structure 620 may include a track 622. Each ofthe UAV supports 630A-D include a roller 632A-D, a gear 634A-D, and amotor 636A-D, respectively.

FIG. 6A depicts the UAV 610 on the landing pad 600, according to anexample embodiment. More particularly, the UAV 610 is on the chargingpad 605 of the landing pad 600. In some examples, electrical power istransferred from the charging pad 605 to the UAV 610 via the electricalcontacts 607. The charging pad 605 may be coupled to an electrical gridin order to recharge batteries within the UAV 610. The UAV 610 mayinclude a plurality of contacts that receive electrical power from thelanding pad 600, and more particularly the charging pad 605. In someembodiments, the fuselage 618 of the UAV 610 may be in electricalcommunication with the charging pad 605. The charging pad 605 may alsofacilitate data communication between the UAV 610 and a network orserver via the electrical contacts 607.

In other examples, the UAV supports 630A-D may include one or moreelectrical contacts in addition to or instead of the electrical contacts607. Electrical contacts on the UAV supports 630A-D may otherwisefunction the same as the electrical contacts 607, but be located as partof the UAV supports 630A-D, including but not limited to being part ofthe roller 632A-D component. In some such examples, the charging pad 605may not include electrical contacts 607 and may no longer be a chargingpad and just physically support the UAV 610 as described herein. Insteador in addition to electrical contacts, the pad may include additionalvisual indicators identifying the pad location. In other examples whereboth the charging pad 605 includes the electrical contacts 607 and thethe UAV supports 630A-D include one or more additional electricalcontacts, the UAV 610 may continue to charge and/or exchange informationvia the electrical contacts of the UAV supports 630A-D after thecharging pad 605 has moved away from the UAV 610 (see FIG. 6D).

As shown in FIG. 6A, the charging pad 605 supports the UAV 610 by beingin contact with a portion of the UAV 610, for example the fuselage 618of the UAV 610. In some embodiments, the UAV 610 may have just landed atthe landing pad 600 in order to recharge batteries of the UAV 610 and/orpick-up/drop-off a payload. The support structure 620 may be coupled toor integrated within a building, truck, or other structure in order tosupport the landing pad 600 and the UAV 610. The support structure 620may be constructed from metal, wood, or other suitable materials. Insome examples, a portion of the support structure 620 may encompassand/or surround the charging pad 605 when the charging pad 605 issupporting the UAV 610.

As described in further detail below (see FIG. 6D), at least a portionof the charging pad 605 is configured to move relative to the supportstructure 620. For example, in FIG. 6A, the charging pad 605 may beconsidered in-plane with a top portion of the support structure 620.However, the charging pad 605 may be rotatably coupled to the supportstructure 620, for example, via the one or more hinges 609. In someaspects, the charging pad 605 may move relative to the support structure620 in order to expose and provide access to an underside of the UAV610. Particularly, moving the charging pad 605 may provide access to thefuselage 618, tether 612, payload coupling apparatus 614, and/or one ormore batteries of the UAV 610.

In FIG. 6A, the UAV supports 630A-D are in a first position. When in thefirst position, the UAV supports 630A-D are along the periphery of thecharging pad 605. In some embodiments, when in the first position, theUAV supports 630A-D may be aligned with or overlapping a portion of thesupport structure 620. The UAV 610 may land on the landing pad 600, orthe charging pad 605, when the UAV supports 630A-D are in the firstposition. Moreover, when in the first position, the UAV supports 630A-Dprovide the UAV 610 access to the charging pad 605. Further, when theUAV supports 630A-D are in the first position, the charging pad 605supports the UAV 610. In some cases, supporting the UAV 610 includessupporting the weight of the UAV 610 and/or maintaining a verticalposition of the UAV 610 relative to a ground surface.

Each of the UAV supports 630A-D are coupled to the support structure620. While four UAV supports 630A-D are shown, it should be understoodthat more and less than four UAV supports are contemplated herein. TheUAV supports 630A-D are movably coupled to the support structure 620. Insome examples, UAV supports 630A-D are movably coupled to the supportstructure 620 via the track 622.

The UAV support 630A are described herein, but it should be understoodthat the other UAV supports 630B-D may include components referencedsimilarly that have similar form and function as the components of theUAV support 630A.

The UAV support 630A includes the motor 636A, the gear 634A, and theroller 632A. The UAV support 630A may also include a second gear on theopposite side of the roller 632A from the gear 634A. Thus the roller632A may be between two gears, for example. The motor 636A may drive thegear 634A to rotate and move along the track 622. The gear 634A movesalong the track 622 such that the roller 632 rolls and/or translatesacross the landing pad 600, the charging pad 605, and the supportstructure 620. In other examples, the gear 634A may include a wheel andrun along a portion of the support structure where the track 622 islocated in FIG. 6A.

The motor 636A may be wired to the electrical power of the landing pad605 including the support structure 620 and the charging pad 605.Moreover, the roller 632A may be considered a bar or a rod. In someregards, the roller 632A is configured to roll or move across at least aportion of the support structure 620 and/or the charging pad 605. Theroller 632A may have a cylindrical shape and may span the charging pad605. The gear 634A may interface and correspond with the track 622 ofthe support structure 620. Moreover, the gear 634A may support theroller 632A.

While depicted and described above as cylindrical and the rollers632A-D, it is contemplated that in other examples the rollers 632A-D maynot roll but only translate across the support structure 620. Moreover,instead of the rollers 632A-D, non-round and/or non-rolling support barsare considered. The shape of the rollers 632A-D may vary based onvarious other parameters including the location of the correspondinglanding pad in the environment as well as the specific function of thoserollers 632A-D in a specific embodiment. For example, in some cases itmay be advantageous to have a flat surface as part of the UAV supports632A-D, and thus cylindrical roller bars may not be used. Other exampleswill be apparent to one of skill in the art without departing from thescope of the invention.

The track 622 may be located along one or more of a top surface or topedge of the support structure 620. In some cases, there may be fourtracks, one on each side of a square or rectangular support structure620.

As depicted, the UAV supports 630A and 630B may both move across thelanding pad 600 in opposite directions along the same track 622.Similarly, the UAV supports 630C and 630D may also both move across thelanding pad 600 in opposite directions. As provided in more detailherein, the UAV supports 630A and 630B may be arranged perpendicular ornearly perpendicular to the UAV supports 630C and 630D. As such, in someexamples, the UAV supports 630A and 630B move perpendicular to themovement of the UAV supports 630C and 630D. Moreover, the UAV supports630A and 630B may overlap the UAV supports 630C and 630D so that thesupports do not conflict or contact one another. In this way, amongother examples, the UAV supports 630A and 630B may be configured at ahigher elevation above the charging pad 605 than the UAV supports 630Cand 630D. In some examples, the gears 634A and 634B may be larger indiameter than the gears 634C and 634D so that the rollers 632A and 632Bare above the rollers 632C and 632D. Other ways to configure the UAVsupports 630A-D and components thereof will be apparent to one ofordinary skill in the art.

Continuing to FIG. 6B, the UAV supports 630A-B are shown translatingacross the support structure from the first position. For example, UAVsupport 630A and UAV support 630 B are closer to one another in FIG. 6Bthan in FIG. 6A. As shown, there are four UAV supports 630A-D, and eachof the four UAV supports 630A-D are moving in a different direction. Inother words, each of the UAV supports 630A-D are moving towards the UAV610. The motors 636A-D are driving the gears 634A-D along the tracks 622such that the rollers 632A-D are moving towards the UAV 610.

In some examples, the plurality of UAV supports 630A-D includes a firstpair of UAV supports 630A-B that move in opposite directions to oneanother, and a second pair of UAV supports 630C-D that move in oppositedirections to one another. Moreover, the first pair of UAV supports630A-B may be perpendicular to the second pair of UAV supports 630C-D.For example, as depicted, the UAV support 630A moves in an oppositedirection compared to the UAV support 630B when moving towards the UAV610. Similarly, the UAV support 630C moves in an opposite directioncompared to the UAV support 630D when moving towards the UAV 610. Inaddition, the UAV supports 630A and 630B are arranged perpendicular tothe UAV supports 630C and 630D.

In FIG. 6C, the UAV supports 630A-D have moved from the first position(e.g., along the periphery of the charging pad 605) to the secondposition. While “position” is used, it should be understood that thefour UAV supports 630A-D are in a first “arrangement” when in the firstposition, for example. The first position may be considered when the UAVsupports 630A-D are along the periphery of the charging pad 605. Inother regards, the first position may be considered the position whentwo UAV supports, such as the pair of UAV supports 630A and 630B arespaced out from one another at a distance of more than three quarters alength or width of the landing pad 600 or charging pad 605. In evenother examples, the first position may be considered the position whenthe UAV support 630A is furthest away from the UAV support 630B, andsimilarly, the UAV support 630C is furthest away from the UAV support630D.

The second position may be considered when the UAV supports 630A-D arefurthest away from the periphery of the charging pad 605. In otherregards, the second position may be considered the position when two UAVsupports, such as the pair of UAV supports 630A and 630B are spaced outfrom one another at a distance of less than one quarter a length orwidth of the landing pad 600 or charging pad 605. In even otherexamples, the second position may be considered the position when theUAV support 630A is closest to the UAV support 630B, and similarly, theUAV support 630C is closest to the UAV support 630D.

Within at least one embodiment, the UAV supports 630A-D have translatedalong and across at least a portion of the support structure 620 fromthe first position to the second position. In the second position, theUAV supports 630A-D are in contact with the UAV 610. In some examples,the UAV supports 630A-D are in contact with a fuselage 618 of the UAV610 when the UAV supports 630A-D are in the second position. In yet afurther embodiment, the UAV supports 630A-D translate across the supportstructure 620 until each of the UAV supports 630A-D come into contactwith the UAV 610 When in the second position, the UAV supports 630A-Dsupport the UAV 610 (e.g., maintain a vertical position of the UAV 610relative a ground surface and/or the landing pad 600).

In some embodiments, the UAV supports 630A-D are force limited such thatthe UAV supports 630A-D translate along the support structure 620 untilthe UAV supports 630A-D contact the UAV 610, but contact with the UAV610 causes the UAV supports 630A-D to stop moving. In other words, whilethe UAV supports 630A-D contact the UAV 610, the UAV supports 630A-D donot cause the UAV 610 to change positions. In this way, the UAV supports630A-D travel to the UAV 610 no matter where the UAV 610 is on thecharging pad 605. Moreover, the UAV supports 630A-D are able to contactand support the UAV 610 without requiring a closed loop control scheme(although it could). In such examples, upon activation, the UAV supports630A-D may operate, for example, translate or move across the supportstructure 620, for a predetermined set of time.

In other embodiments, in addition to being force limited, or instead ofbeing force limited, the UAV supports 630A-D are time limited orconfigured to move a predetermined distance along the support structure620. In some examples, after the movement of the UAV supports 630A-D isforce limited, the UAV supports 630A-D may then move for thepredetermined time or distance. The UAV supports 630A-D may move aparticular distance or time such that the UAV supports 630A-D contactthe UAV 610 but do not contact the fuselage 618 in order to preventpossible scratching, marking, or damaging the fuselage 618. In such acase, the UAV supports 630A-D may contact a different section of the UAV610, such as a boom or wing of the UAV 610.

In further examples, the UAV supports 630A-D are able to move the UAV610. For example, it is contemplated that the UAV supports 630A-D canmove the UAV 610 across the landing pad 600 to a specific location, orfor example, may rotate the UAV 610 to a certain orientation in order tobetter support the loading/unloading and/or charging processes.

Because the UAV supports 630A-D are supporting the UAV 610 when the UAVsupports 630A-D are in the second position, the charging pad 605 is nolonger supporting the UAV 610. As such, and as shown in FIG. 6D, thecharging pad 605 may move relative to the support structure 620. In someexamples, the charging pad 605 has moved away from the UAV 610. In FIG.6D, the charging pad 605 rotates relative to the support structure 620,and particularly a top portion of the support structure 620. Thecharging pad 605 may include a latch(s), bracket(s), support(s) and/orthe hinge(s) 609 coupled to the support structure 620 so that thecharging pad 605 can be moved away from the UAV 610. In some examples,the support structure 620 may include one more motors that operate thecharging pad 605. In some examples, the charging pad 605 may be biasedopen or closed via one or more springs or actuators positioned betweenthe charging pad 605 and the support structure 620. After being movedaway from the UAV 610, an underside of the UAV 610 is accessible.

While the charging pad 605 is rectangular in shape in FIGS. 6A-6G, itshould be understood that other shapes are considered. Moreover, while asingle charging pad 605 is depicted, more than one charging pad iscontemplated herein (see e.g., FIG. 7 ). In some examples, the chargingpad 605 may include at least two components that move independently ofone another. In another example, there may be at least two separatecharging pads that are each supported by the support structure 620.Other designs and configurations are known to people of skill in theart.

Moreover, while the charging pad 605 is shown moving away from the UAV610, it should be understood that other similar operations arecontemplated by this arrangement. For example, the charging pad 605 maybe moved towards the UAV 610 in order to cause the charging pad 605 tocome into contact with the UAV 610 in order to carry out an operation,such as recharge one or more batteries of the UAV 610.

In FIG. 6E, the UAV 610 has payed out (or deployed) at least a portionof the retractable tether 612 including the payload coupling apparatus614. A distal end of the tether 612 is coupled to the payload couplingapparatus 614, while a proximate end of the tether is coupled to the UAV610. As described above, the UAV 610 may further include a winch system(not shown) that operates the tether 612. Although not shown, if the UAV610 were making a delivery, the payload coupling apparatus 614 could becoupled to a payload and the tether 612 could be lowering the payload tobe unloaded. As depicted, a payload, such as the payload 616 (see FIG.6F) may be loaded onto the payload coupling apparatus 614 from thisposition. In some examples, the UAV 610 loads a payload and/or begins aloading sequence when the UAV supports 630A-D are in the secondposition. One or more sensors on the UAV 610 may recognize an increasein the tension of the tether 612 and register that a payload has beenloaded.

In some examples, the UAV supports 630A-D may move to a third positionduring the loading process. For example, in preparing to lower thepayload coupling apparatus 614, the UAV supports 630A-D may move apartfrom one another so that a cavity or spacing under the UAV 610 andbetween UAV Supports 630A-D is large enough to fit the payload couplingapparatus 614 and the payload 616 through the cavity. In other example,as shown in FIG. 6E, in preparing to retract the payload 616 (not shownuntil FIG. 6F), the UAV supports 630A-D may move apart from one anotherso that a cavity or spacing under the UAV 610 and between UAV Supports630A-D is large enough to fit the payload 616 through the cavity.Nonetheless, as described above, in some examples, the payload 616 maystill be loaded to the UAV 610 when the UAV supports 630A-D are in thesecond position. In yet another example, the UAV supports 630A-D maymove to the third position when the charging pad 605 has moved away fromthe UAV 610.

Continuing to FIG. 6F, the payload 6F has been coupled to the payloadcoupling apparatus 614 of the UAV 610 and the UAV 610 has reeled in thetether 612 in preparation for departure from the landing pad 600. Asshown in FIGS. 6E and 6F, the UAV supports 630A-D may move to the thirdposition in preparation for accepting the payload 616. The thirdposition may be somewhere between the first position and the secondposition. In the third position, the UAV supports 630A-D still supportthe UAV 610. However, in some examples, when in the third position, theUAV supports 630 may support the UAV 610 by contacting the UAV 610 in adifferent location than when the UAV supports 630 were in the secondposition. In some examples, the UAV supports 630A-D may not no longer bein contact with the fuselage 618 of the UAV 610, but be in contact withanother portion of the UAV 610. At least some of the UAV supports 630may be further spaced apart when in the third position such that thepayload 616 fits through a cavity under the fuselage 618 of the UAV 610.

FIG. 6G depicts the UAV 610 departing from the landing pad 600. Uponactivation of the propellers of the UAV 610, the UAV 610 may begin tohover above the landing pad 600. Moreover, upon hovering and the UAV 610no longer being in contact with the UAV supports 630, the UAV supports630 may return to the first position or move to a position closer to thefirst position. In this way, the cavity that the payload will movethrough under the UAV 610 becomes larger and thus it is less likely thatthe payload 616 contacts or conflicts with the UAV supports 630.

While the payload 616 is reeled all the way up to the UAV 610 in FIG. 6Fand then the UAV departs as shown in FIG. 6G, it should be understoodthat in some examples the UAV 610 may begin to hover before the payload616 is fully loaded or reeled in. For example, one loading sequencecould include the payload 616 being coupled to the coupling apparatus614, and upon sensing the payload 616 the UAV 610 may begin to hover andtakeoff from the UAV supports 630A-D. The UAV supports 630A-D may be inthe second position at this time. Then, once the UAV 610 is hovering,the UAV supports 630A-D may move from the second position to the thirdor the first position to allow the payload 616 to continue to be reeledup to the UAV 610. The UAV 610 may then load the payload 616 all the wayto the fuselage 618 and depart the landing pad 600.

Again, it will be understood to a person of skill in the art that theoperations described above and herein may also be executed in anotherorder, such as a reverse order, and still function. For example, the UAV610 may arrive with the payload 616 as shown in FIG. 6G, land asdepicted in FIG. 6F, unload the payload 616 as depicted in FIG. 6E, etc.

FIG. 7 depicts a landing pad 700, a first charging pad 605A, a secondcharging pad 605B, the UAV 610, the support structure 620, and theplurality of UAV supports 630. FIG. 7 and the components shown thereinmay be similar in form and function to those shown in FIG. 6D. However,as shown in FIG. 7 , other configurations of charging pads, such as thefirst charging pad 605A and the second charging pad 605B, are consideredherein. As shown in FIG. 7 , the two charging pads 605A and 605B mayboth move relative to the support structure 620. Further, each of thetwo charging pads 605A and 605B may be hinged and/or motorized to moverelative to the UAV 610 when the UAV 610 is being supported by the UAVsupports 630A-D. For example, the first charging pad 605A may be coupledto the support structure 620 via one or more hinges 609A. Similarly, thesecond charging pad 605B may be coupled to the support structure 620 viaone or more hinges 609B. Moreover, although not depicted it should benoted that the two charging pads 605A and 605B may separately ortogether support the UAV 610 when the UAV supports 630A-B are in thefirst position.

Additionally, a method for supporting and charging a UAV is disclosed.FIG. 8 is a simplified block diagram illustrating a method 800 forsupporting a UAV on a landing pad. It should be understood that examplemethods, such as method 800, might be carried out by one or moreentities, or combinations of entities (i.e., by other computing devices,and/or combinations thereof), without departing from the scope of theinvention.

For example, functions of the method 800 may be fully performed by amachine, a human operator, a computing device (or components of acomputing device such as one or more processors or controllers), or maybe distributed across multiple components of the computing device,across multiple computing devices, and/or across one or more servers. Insome examples, the computing device may receive information from inputcommands initiated by an operator, sensors of the computing device, ormay receive information from other computing devices that collect theinformation. More particularly, functions of the method 800 may becarried out by computing device(s) and/or controller(s) of a UAV, orthat of a UAV system or network, or a combination thereof.

As shown by block 802, the method 800 includes supporting a UAV above aground surface by a charging pad of a landing pad. The charging pad maybe coupled to a support structure as part of a payload loading system,for example. The landing pad and payload loading system may be part of aUAV delivery system or service. The landing pad may be coupled toexisting structures, or in other examples the landing pad may beinstalled as a new structure. The landing pad may be located at merchantterminals or modules, food trucks, warehouses, distribution centers,residences, within communities, etc., among other locations.

The UAV may have received instructions from a UAV network or system toexecute an operation at or on the landing pad. For example, the UAV maybe sent to the landing pad to pick up a payload for delivery. Or, inanother example, the landing pad may be registered within a UAV systemor network and the UAV may autonomously determine that the UAV shouldland to carry out a certain operation, such as charge its batteries.

As shown by block 804, the method 800 includes charging at least onebattery of the UAV. In one embodiment, charging the battery of the UAVmay be executed via the charging pad, and more particularly electricalcontacts within the charging pad that transfer electrical power to theUAV. The UAV, including but not limited to the fuselage of the UAV mayinclude contacts that receive the electrical power from the charging padand route the power to one or more batteries of the UAV. Moreover, thecharging pad may transfer data to the UAV via the electrical contacts.

The charging pad may provide power to the UAV automatically upon the UAVlanding on the landing pad, or upon a command issued by the UAV, a user,or a UAV system/network. Moreover, the charging may stop charging theUAV upon instructions from the UAV, a user, or a UAV system/network.

As shown by block 806, the method 800 includes a plurality of UAVsupports moving across the landing pad towards the UAV. In some examplesthe UAV supports may translate across the landing pad. The UAV supportsmay be similar to the UAV supports 630 described in FIGS. 6A-6G, forexample. The UAV supports may each move in a different direction toreach the UAV that has landed on the charging pad. In some examples,moving the plurality of UAV supports across the landing pad towards theUAV may stop when the plurality of UAV supports come into contact withthe UAV.

Instructions to the landing pad may initial the movement of the UAVsupports. The UAV supports may be triggered to move based on a varietyof operational scenarios. For example, the UAV supports may beautomatically triggered to move based on the charging pad stoppingproviding electrical power to the UAV. Or the UAV supports may betriggered to move directly by the UAV upon the UAV batteries reaching acertain predetermined capacity. In other examples, upon a userapproaching the landing pad to interact with the UAV (to begin theprocess to make or receive a delivery, for example), the UAV supportsmay move towards the UAV. In yet another example, the UAV supports maybe instructed to move towards the UAV based on a command received from aUAV network. A variety of similar operational parameters are understoodto those of skill in the art in view of the disclosure provided herein.

As shown by block 808, the method further includes moving the chargingpad away from the UAV. In some examples, the movement may include arotation of the charging pad via one or more hinges between the chargingpad and the support structure. The charging pad may be moved away fromthe UAV after the UAV supports move towards the UAV. More particularly,the charging pad may be moved away from the UAV after the UAV supportscontact and provide support to the UAV. As such, the plurality of UAVsupports provide support to the UAV above the ground surface.

The charging pad and/or the support structure may receive instructionsto move the charging pad away from the UAV upon confirmation that theUAV supports have come into contact with the UAV. Alternatively, thecharging pad may be moved away from the UAV after a predetermined amountof time after the UAV supports were initiated to move across the landingpad.

As provided in block 810, the method 800 also includes providing accessto an underside of the UAV. The underside of the UAV is accessible whenthe charging pad has moved away from the UAV (see block 808) and the UAVis being supported by the UAV supports and not the charging pad (seeblock 806).

The method 800 may include other steps not shown in FIG. 8 . Forexample, the method 800 may include loading a payload to the UAV afterthe charging pad has moved away from the UAV and the UAV is supported bythe plurality of UAV supports. In another example, the method 800 mayinclude the actual landing or takeoff operations of the UAV. Thus, themethod may include landing the UAV on the charging pad of the landingpad, for example.

Blocks or steps of method 800 may be controlled or initiated based oninitiation of a payload loading sequence. For example, a user mayinitiate a pick up request with a UAV network. A UAV may then beinstructed to initiate a landing operation onto the landing pad. Detailsof the pick up request may provide the parameters of the delivery theuser is attempting to accomplish. Based on those details, the UAV maycompare its current battery life against an estimated or known amount offly time or other parameter to carry out the delivery. The UAV maydetermine that additional power is necessary, and thus begin accepting acharge from the charging pad of the UAV. The UAV may also exchangeinformation (e.g., status of the UAV systems, among others) with the UAVnetwork via being connected to the charging pad. Upon recharging itsbatteries to enough of a capacity to execute the delivery, the UAV maycontinue the loading sequence. This may trigger the UAV supports to movetowards the UAV and eventually contact the UAV.

Upon the UAV supports now supporting the UAV, the charging pad mayautomatically or manually be moved away from the UAV such that access tothe underside of the UAV is provided. Upon the underside of the UAVbeing accessible, the UAV may deploy its tether and payload couplingapparatus. Upon the payload coupling apparatus the UAV may wait toeither automatically detect or be told that a payload has been loaded.The UAV may then reel in the payload and prepare for departure. The UAVsupports may be configured to move apart from one another in order toallow for the payload to fit between the supports. The UAV may theninitiate a take off operation, including taking off from the UAVsupports of the landing pad.

In some examples, after loading the payload to the UAV, a takeoff of theUAV may be initiated. For example, the UAV may begin to hover above thesupports. The supports may sense that the weight of UAV is no longer onthe supports or the system may be commanded that the UAV is no longerbeing supported by the supports. Upon the supports no longer supportingthe UAV, the plurality of supports may move outwards towards the supportstructure. In at least one embodiment, as soon as the UAV begins tohover the UAV supports may be commanded to move away from the UAV and/ortowards the periphery of the landing pad or support structure such thatpotential conflict between the payload and the supports is reduced.

In further examples, instead of the rollers of the UAV supports beingmotorized, the rollers may be driven mechanically only via a mechanismthat translates a downward motion or lowering motion of the charging padinto lateral motion of the UAV supports and rollers. Such an embodimentmay reduce a number of electrical components and correspondingly reducecosts.

Other similar sequences (replacing/exchanging batteries or othercomponents, unloading, other servicing, etc.) will be known to a personof skill in the art without departing from the scope of this disclosure.Moreover, means for providing, initiating, and communicatinginstructions for carrying out such a sequence are also considered.

In other embodiments the method 800 may include more or less blocks aswell as blocks that carry out various functions described herein. Also,while the blocks are expressed in a specific order herein, otherordering of the various blocks is considered herein.

VI. CONCLUSION

It should be understood that arrangements described herein are forpurposes of example only. As such, those skilled in the art willappreciate that other arrangements and other elements (e.g. machines,interfaces, operations, orders, and groupings of operations, etc.) canbe used instead, and some elements may be omitted altogether accordingto the desired results. Further, many of the elements that are describedare functional entities that may be implemented as discrete ordistributed components or in conjunction with other components, in anysuitable combination and location, or other structural elementsdescribed as independent structures may be combined.

While various aspects and implementations have been disclosed herein,other aspects and implementations will be apparent to those skilled inthe art. The various aspects and implementations disclosed herein arefor purposes of illustration and are not intended to be limiting, withthe true scope being indicated by the following claims, along with thefull scope of equivalents to which such claims are entitled. It is alsoto be understood that the terminology used herein is for the purpose ofdescribing particular implementations only, and is not intended to belimiting.

We claim:
 1. A landing pad for an unmanned aerial vehicle (“UAV”),comprising: a support structure; a charging pad coupled to the supportstructure such that at least a portion of the charging pad is configuredto move relative to the support structure; and a plurality of UAVsupports coupled to the support structure, wherein the plurality of UAVsupports are configured to translate along the support structure from afirst position to a second position, wherein when in the first positionthe plurality of UAV supports provide the UAV access to the charging padand the charging pad supports the UAV, and wherein when in the secondposition the plurality of UAV supports support the UAV, wherein each ofthe plurality of UAV supports are force limited such that the pluralityof UAV supports are configured to translate along the support structureuntil the plurality of UAV supports contact the UAV but do not cause theUAV to change position.
 2. The landing pad of claim 1, wherein when theplurality of UAV supports are in the second position, the charging padis configured to move away from the UAV such that an underside of theUAV is accessible.
 3. The landing pad of claim 1, wherein the UAV isconfigured to load a payload when the plurality of UAV supports are inthe second position.
 4. The landing pad of claim 1, wherein theplurality of UAV supports are configured to translate along the supportstructure until each of the plurality of UAV supports contacts the UAV.5. The landing pad of claim 1, wherein when in the second position, eachof the plurality of UAV supports is in contact with the UAV.
 6. Thelanding pad of claim 1, wherein the UAV is configured to land on thelanding pad when the plurality of UAV supports are in the firstposition.
 7. The landing pad of claim 1, wherein the UAV is configuredto takeoff from the landing pad when the plurality of UAV supports arein a third position.
 8. The landing pad of claim 1, wherein the UAV isconfigured to deploy a payload coupling apparatus when the plurality ofUAV supports are in the second position.
 9. The landing pad of claim 1,wherein the plurality of UAV supports are configured to translate alongthe support structure for a predetermined amount of time.
 10. Thelanding pad of claim 1, wherein the charging pad is configured to chargea battery of the UAV when the plurality of UAV supports are in the firstposition.
 11. The landing pad of claim 1, wherein each of the pluralityof UAV supports comprises a roller, wherein the roller spans thecharging pad, and wherein the roller is configured to roll along aportion of the support structure.
 12. The landing pad of claim 1,wherein each of the plurality of UAV supports comprises a gear wheelcoupled to a bar, wherein the bar spans the charging pad, and whereinthe support structure comprises a track corresponding to the gear wheel.13. The landing pad of claim 1, wherein the plurality of UAV supportsare located along a periphery of the charging pad when in the firstposition.
 14. The landing pad of claim 1, wherein the plurality of UAVsupports comprises: a first pair of UAV supports that move in oppositedirections to one another; and a second pair of UAV supports that movein opposite directions to one another, wherein the first pair of UAVsupports are pendicular to the second pair of UAV supports.
 15. Amethod, comprising: supporting an unmanned aerial vehicle (“UAV”) abovea ground surface by a charging pad of a landing pad; moving a pluralityof UAV supports across the landing pad towards the UAV, wherein each ofthe plurality of UAV supports moves in a different direction; and aftermoving the plurality of UAV supports towards the UAV, moving thecharging pad away from the UAV such that the UAV is no longer supportedby the charging pad and the plurality of UAV supports support the UAVabove the ground surface.
 16. The method of claim 15, furthercomprising: loading a payload to the UAV after the charging pad hasmoved away from the UAV and the UAV is supported by the plurality of UAVsupports.
 17. The method of claim 16, further comprising: after loadingthe payload to the UAV, initiating a takeoff of the UAV; and afterinitiating the takeoff, moving the plurality of UAV supports away fromthe UAV such that the UAV is no longer supported by the plurality of UAVsupports.
 18. The method of claim 15, wherein the moving the pluralityof UAV supports across the landing pad towards the UAV stops when theplurality of UAV supports contact the UAV.
 19. A payload loading system,comprising: an unmanned aerial vehicle (UAV) that comprises a fuselageand a retractable tether, wherein a distal end of the tether is coupledto a payload coupling apparatus, and a proximate end of the tether iscoupled to the UAV; and a landing pad, comprising: a support structure;a charging pad coupled to the support structure such that at least aportion of the charging pad is configured to move relative to thesupport structure; and a plurality of UAV supports coupled to thesupport structure, wherein the plurality of UAV supports translate alongthe support structure from a first position to a second position,wherein when in the first position the plurality of UAV supports providethe UAV access to the charging pad and the charging pad supports theUAV, and wherein when in the second position the plurality of UAVsupports are in contact with the fuselage of the UAV wherein each of theplurality of UAV supports are force limited such that the plurality ofUAV supports are configured to translate along the support structureuntil the plurality of UAV supports contact the UAV but do not cause theUAV to change position.